v9.2.0.1
llandale - Wed Oct 20 15:20:02 EDT 2010 |
Re: Config/menuFns.inc 784
void unLockSection() {
... UnlockDiscardSection (...) // Line 784
}
Mathias Mamsch, IT-QBase GmbH, Consultant for Requirement Engineering and D00RS
|
Re: Config/menuFns.inc 784 Mathias Mamsch - Thu Oct 21 13:35:55 EDT 2010
void unLockSection() {
... UnlockDiscardSection (...) // Line 784
}
Mathias Mamsch, IT-QBase GmbH, Consultant for Requirement Engineering and D00RS
So this says that somewhere in my code I'm calling function 'unLockSection', and THAT function is calling UnlockDiscardSection? Did you misspell that, should be lower case "*u*nlockDiscardSection"? Too bad, nowhere in my code am I calling 'unLockSection', but I do issue unlockDiscardSection at about the place in the code the user claims I'm getting this error.
|
Re: Config/menuFns.inc 784 llandale - Thu Oct 21 16:53:30 EDT 2010
Regards, Mathias Mathias Mamsch, IT-QBase GmbH, Consultant for Requirement Engineering and D00RS |
Re: Config/menuFns.inc 784 Mathias Mamsch - Fri Oct 22 07:00:02 EDT 2010 Mathias Mamsch, IT-QBase GmbH, Consultant for Requirement Engineering and D00RS But the code indeed deals with this module in shared mode, but more importantly that other (invisible) module in shared mode, where the code needs to lock that other section, create objects and/or links, and unlock that section saving or discarding changes. I have had some trouble in the past where the code gets Module and Object handles from that other module which get corrupted when that module is manually closed. The code is 10,000 lines and frankly a nightmare to navigate, in spite of my best efforts are reasonable standards. One big issue is that the User's recount of events does not match the screen shot he's given me about it. He says the problem occurs some time after pressing a button on one of my dialogs, but the screen shot shows that button is disabled on that dialog. Will investigate anyway, but its inconcievable he has some special Triggers or Layouts or whatever. Thanks for the help, not sure how to proceed. Cannot reproduce the error.
|